(y)

(n)

(o)

%

Q5

Do you always send DATE-TIME values with a timezone?

9

9

1

47%

Q6

Do you always send DATE-TIME values in UTC or floating?

9

5

5

47%

Q7

Do you provide a standard set of timezones built-in to your product?

16

3

0

84%

Q8

Where did you get your timezone definitions?

Most come from Olsen. Some from Windows. Others from Java.

Q9

How many timezone definitions do you have?

Varies from about 50 to about 380

Q10

Do you have a special naming scheme for TZIDs, and if so what is it?

Olsen naming e.g. America/New_York. Windows naming. Tzid: URI. Tzid with vendor prefix.

Q11

Do you provide a mechanism for updating built-in timezones?

5

9

1

33%

Q12

Do you adjust future times to account for timezone definition changes?

2

3

3

25%

Q13

Do you accept and use timezone definitions from imported iCalendar data?

10

5

1

63%

Q14

Do you attempt to merge timezone definitions with the same TZID when importing iCalendar data?

Some do, some don’t (about 50%). Also: “We match it to our internal list by ID first and then by rule”.

Q15

When exporting timezones in iCalendar data (either to a file or via iTIP) do you send the entire timezone definition or just the set of dates needed for coverage of the event?

Those that do it export the entire timezone definition.

Q16

Would you use timezone definitions from a standard timezone registry if one were created?

11

2

4

65%

Q17

What problems would be involved in changing a timezone definition if DST was changed at some point in the future?

Most would need to get new definitions and update with automatically or manually. There was some concern about how the new definitions would look (e.g. some could not support more than one STANDARD or DAYLIGHT component).

C1

Comments on specific answers (include Q number for cross-reference to original question):

C2

Comments on the format and ease of use of this questionnaire:

Most liked email (though some wanted text/plain and not text/html). A few preferred web-based. One wanted MS Word file.

C3

Are there any additional questions we should be asking, and if so what are they?

Should have asked: Do any applications support multiple STANDARD and DAYLIGHT components? Should have asked: how do you treat ‘foreign’ TZIDs (e.g. map to own internal TZID etc)? Would like TZID on RRULE to simplify some problems.Should have asked: are timezones used on simple non-recurring events, or only recurring events?